Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d69af18be09b39d18fa50c85fad3c083f8237274ddcb7fdc9fc39e1c8dff788b

Tx prefix hash: 45189ab79aef34e535a5abe63995a14c342768228e9222d75a9f92b03b8f037b
Tx public key: 32fce0911b87c08a9a5153bd1d6a2c524fbd4f7bbd1921b07f84be7ed40c8839
Timestamp: 1764906488 Timestamp [UCT]: 2025-12-05 03:48:08 Age [y:d:h:m:s]: 00:023:09:34:19
Block: 1426726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16750 RingCT/type: yes/0
Extra: 0132fce0911b87c08a9a5153bd1d6a2c524fbd4f7bbd1921b07f84be7ed40c883902110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c7bfe2b61d53da5f753857a126b68640812ae7e4b263766c0463d13d05a8ceb 0.600000000000 1915419 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": 1426736, "vin": [ { "gen": { "height": 1426726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c7bfe2b61d53da5f753857a126b68640812ae7e4b263766c0463d13d05a8ceb" } } ], "extra": [ 1, 50, 252, 224, 145, 27, 135, 192, 138, 154, 81, 83, 189, 29, 106, 44, 82, 79, 189, 79, 123, 189, 25, 33, 176, 127, 132, 190, 126, 212, 12, 136, 57, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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