Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d18ede89229601aca8983cd8be4865e3a17c97f8dddb4452dc1d241cf5e53e84

Tx prefix hash: eb0d4740f9a422de39cd2e1a9edba04918518f252e721420ccbc1784a4fe708f
Tx public key: 6a29f07f6e0fbdae7e3633272fa7248b856a3d3ce2fd911ef9356d0143a92c9a
Timestamp: 1719303903 Timestamp [UCT]: 2024-06-25 08:25:03 Age [y:d:h:m:s]: 01:136:15:05:04
Block: 1051784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356187 RingCT/type: yes/0
Extra: 016a29f07f6e0fbdae7e3633272fa7248b856a3d3ce2fd911ef9356d0143a92c9a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5aa86d40348ca4d4ae4c922ee1ec9821b55c94eb7bd23c4add0f2c5c43d6a4f 0.600000000000 1522103 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": 1051794, "vin": [ { "gen": { "height": 1051784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5aa86d40348ca4d4ae4c922ee1ec9821b55c94eb7bd23c4add0f2c5c43d6a4f" } } ], "extra": [ 1, 106, 41, 240, 127, 110, 15, 189, 174, 126, 54, 51, 39, 47, 167, 36, 139, 133, 106, 61, 60, 226, 253, 145, 30, 249, 53, 109, 1, 67, 169, 44, 154, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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