Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53782b28d47619c5d20c3f87ae7ba9d27974b7e0b0bc1cf36dd7b14947995dd6

Tx prefix hash: 6bb44e1cdac6a0568823e11e5b5be07f7d733473e0da0c18c75609dbe9bf235c
Tx public key: 3d6c1ef6834afa7f63f38d33b83921e8bf79f92c93183435bfa15ce1fb781b65
Timestamp: 1737310463 Timestamp [UCT]: 2025-01-19 18:14:23 Age [y:d:h:m:s]: 00:149:21:21:25
Block: 1200891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106848 RingCT/type: yes/0
Extra: 013d6c1ef6834afa7f63f38d33b83921e8bf79f92c93183435bfa15ce1fb781b65021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a351a22ecc82a50be9042580d72d531ffd3964ca05953ba48b026fa221b77c14 0.600000000000 1687538 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": 1200901, "vin": [ { "gen": { "height": 1200891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a351a22ecc82a50be9042580d72d531ffd3964ca05953ba48b026fa221b77c14" } } ], "extra": [ 1, 61, 108, 30, 246, 131, 74, 250, 127, 99, 243, 141, 51, 184, 57, 33, 232, 191, 121, 249, 44, 147, 24, 52, 53, 191, 161, 92, 225, 251, 120, 27, 101, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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