Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a332f9ce31117dc199e8f1db88d5093c5c4819cb91a857512c61162ac3c0bcb8

Tx prefix hash: 41a904fc2b76f80fce2cd4b99a684e51d3d9e35b4b16f548d042fa353771d1eb
Tx public key: 8a00df1f895999117f2a32f2c167df917335257259b7962771ea754d464e55b6
Timestamp: 1706668208 Timestamp [UCT]: 2024-01-31 02:30:08 Age [y:d:h:m:s]: 01:283:04:22:01
Block: 947009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461188 RingCT/type: yes/0
Extra: 018a00df1f895999117f2a32f2c167df917335257259b7962771ea754d464e55b602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61408897e710564feaab95f7d1d2bd0f86c4ef5bbc187f7da87cbf293c3389b7 0.600000000000 1405355 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": 947019, "vin": [ { "gen": { "height": 947009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61408897e710564feaab95f7d1d2bd0f86c4ef5bbc187f7da87cbf293c3389b7" } } ], "extra": [ 1, 138, 0, 223, 31, 137, 89, 153, 17, 127, 42, 50, 242, 193, 103, 223, 145, 115, 53, 37, 114, 89, 183, 150, 39, 113, 234, 117, 77, 70, 78, 85, 182, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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