Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee2251801b67c7b2f0b3ca2a7f6069b4e781e9773d2d66541ba1a89e8ab8ccf6

Tx prefix hash: 11580c248ab30a3690273467cf55507350ae50d17485853952cde3b34be3b930
Tx public key: b040361142d5ef6f7d623c9daa84435e086b2858c02d6f4988085b1dc0032c2b
Timestamp: 1730552528 Timestamp [UCT]: 2024-11-02 13:02:08 Age [y:d:h:m:s]: 00:166:00:59:38
Block: 1144954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118508 RingCT/type: yes/0
Extra: 01b040361142d5ef6f7d623c9daa84435e086b2858c02d6f4988085b1dc0032c2b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46619247e1aa2b0285268ccfad7fe6e60ea9244af562f39232103e761319dd80 0.600000000000 1629305 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": 1144964, "vin": [ { "gen": { "height": 1144954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46619247e1aa2b0285268ccfad7fe6e60ea9244af562f39232103e761319dd80" } } ], "extra": [ 1, 176, 64, 54, 17, 66, 213, 239, 111, 125, 98, 60, 157, 170, 132, 67, 94, 8, 107, 40, 88, 192, 45, 111, 73, 136, 8, 91, 29, 192, 3, 44, 43, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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