Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0976568d40c233985e133d37a4c429c18add7bb55fae63e2d2094fac5a16ae55

Tx prefix hash: 372fbbdbe487769a76c12fde127c28309ea5c7e88520b3cb0bf7492f2878fec0
Tx public key: 21f00c94f241002d3c1d483b7e9b27f56f13f716f3ba0f0d96b7b9f10745e43d
Timestamp: 1694284731 Timestamp [UCT]: 2023-09-09 18:38:51 Age [y:d:h:m:s]: 01:204:12:09:11
Block: 844544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407264 RingCT/type: yes/0
Extra: 0121f00c94f241002d3c1d483b7e9b27f56f13f716f3ba0f0d96b7b9f10745e43d02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.976506651000 dcy

stealth address amount amount idx
00: 82eb2aeeec79780b713acbef06c9b71d78b1b5b99e7885d7a44b1c0711949723 0.976506651000 1297858 of 0

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": 844554, "vin": [ { "gen": { "height": 844544 } } ], "vout": [ { "amount": 976506651, "target": { "key": "82eb2aeeec79780b713acbef06c9b71d78b1b5b99e7885d7a44b1c0711949723" } } ], "extra": [ 1, 33, 240, 12, 148, 242, 65, 0, 45, 60, 29, 72, 59, 126, 155, 39, 245, 111, 19, 247, 22, 243, 186, 15, 13, 150, 183, 185, 241, 7, 69, 228, 61, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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