Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dd648aec2864b4d06348094129647ab59830ed587e88dc9d457d7e34e655a3a

Tx prefix hash: a7b7dbfa19297afa2dc5579bc14d59d6abc7cf0abb00962a84af1a411a9dbed5
Tx public key: d46d6095493363087f1fd8a66a7eef66a06f473e5bbbaf1af256860a9f172c19
Timestamp: 1737700595 Timestamp [UCT]: 2025-01-24 06:36:35 Age [y:d:h:m:s]: 00:144:19:59:03
Block: 1204111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103245 RingCT/type: yes/0
Extra: 01d46d6095493363087f1fd8a66a7eef66a06f473e5bbbaf1af256860a9f172c190211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 632d032c28b39e2e359ae29fefaeb321f0e4fe27fd25bc7d912872d7e2c41fe7 0.600000000000 1690794 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": 1204121, "vin": [ { "gen": { "height": 1204111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "632d032c28b39e2e359ae29fefaeb321f0e4fe27fd25bc7d912872d7e2c41fe7" } } ], "extra": [ 1, 212, 109, 96, 149, 73, 51, 99, 8, 127, 31, 216, 166, 106, 126, 239, 102, 160, 111, 71, 62, 91, 187, 175, 26, 242, 86, 134, 10, 159, 23, 44, 25, 2, 17, 0, 0, 0, 5, 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