Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9788ac5808268f264dddc65b20b161ac53b1ade81dfd5eed6e6bb5a0eb8e3363

Tx prefix hash: 945768d665fa22f9c043d82f9e032452f3b6d802a08b89fff51a58153cb9325a
Tx public key: 99c6c1b0407800f8666463c05d339c6fc231824d6772caccab5a0a9fdcc7486d
Timestamp: 1740253074 Timestamp [UCT]: 2025-02-22 19:37:54 Age [y:d:h:m:s]: 00:228:08:06:02
Block: 1224991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160914 RingCT/type: yes/0
Extra: 0199c6c1b0407800f8666463c05d339c6fc231824d6772caccab5a0a9fdcc7486d02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba6982b3979367d373f13bd923695a0408005928ea1fa6db4a17e04b3bce8d4e 0.600000000000 1711856 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": 1225001, "vin": [ { "gen": { "height": 1224991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba6982b3979367d373f13bd923695a0408005928ea1fa6db4a17e04b3bce8d4e" } } ], "extra": [ 1, 153, 198, 193, 176, 64, 120, 0, 248, 102, 100, 99, 192, 93, 51, 156, 111, 194, 49, 130, 77, 103, 114, 202, 204, 171, 90, 10, 159, 220, 199, 72, 109, 2, 17, 0, 0, 0, 12, 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