Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 93974c0f4dac37e1891cd8df5ccb5f2226d8286be31f34a58e6f52921685f089

Tx prefix hash: f4a40f58b68873995c9152c6b7d6c3f05550ca526eabe44b9bd17b307cd03a84
Tx public key: f739cd60de288470c11b7e1863f265d897bbb90354a7276d851de30dae91a02f
Timestamp: 1706928002 Timestamp [UCT]: 2024-02-03 02:40:02 Age [y:d:h:m:s]: 01:025:09:34:47
Block: 949168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279184 RingCT/type: yes/0
Extra: 01f739cd60de288470c11b7e1863f265d897bbb90354a7276d851de30dae91a02f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76afb709f26381dc2f37dce79bea3e0d75a7444de7730d73d914b6df2aa1612c 0.600000000000 1407690 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 949178, "vin": [ { "gen": { "height": 949168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76afb709f26381dc2f37dce79bea3e0d75a7444de7730d73d914b6df2aa1612c" } } ], "extra": [ 1, 247, 57, 205, 96, 222, 40, 132, 112, 193, 27, 126, 24, 99, 242, 101, 216, 151, 187, 185, 3, 84, 167, 39, 109, 133, 29, 227, 13, 174, 145, 160, 47, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8