Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9de8c40e23fa51ad49bbc281e833ec184cabde888d764418cd6a8b97959e46e

Tx prefix hash: 9b95113e7bab1b287ce4477bff011462db88956598d5054ffb943adcbf0c1453
Tx public key: 15713c541d8d2d6a371eb98a4a582905a4e3c1292c26ead1fd8e4446f96cbf7e
Timestamp: 1706875742 Timestamp [UCT]: 2024-02-02 12:09:02 Age [y:d:h:m:s]: 01:026:00:47:40
Block: 948742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279646 RingCT/type: yes/0
Extra: 0115713c541d8d2d6a371eb98a4a582905a4e3c1292c26ead1fd8e4446f96cbf7e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e523db063a23714e00db4c9baa567881205be954aeab76845adba56f08e7917f 0.600000000000 1407216 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": 948752, "vin": [ { "gen": { "height": 948742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e523db063a23714e00db4c9baa567881205be954aeab76845adba56f08e7917f" } } ], "extra": [ 1, 21, 113, 60, 84, 29, 141, 45, 106, 55, 30, 185, 138, 74, 88, 41, 5, 164, 227, 193, 41, 44, 38, 234, 209, 253, 142, 68, 70, 249, 108, 191, 126, 2, 17, 0, 0, 0, 1, 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