Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e31f6d960e6cb972fefc44e1938e5c5c5ee5e46a7fb64a2bbeb60d837ac7c32d

Tx prefix hash: adcee9b1fc4652ae7ccc110ea3e22054dfb04519169df5da1569af215a17c1e7
Tx public key: 747aee90eec98514a2f2f43e332c2da522f3046df9ce405591cad107bf3b10b5
Timestamp: 1717050186 Timestamp [UCT]: 2024-05-30 06:23:06 Age [y:d:h:m:s]: 00:154:18:26:16
Block: 1033106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110779 RingCT/type: yes/0
Extra: 01747aee90eec98514a2f2f43e332c2da522f3046df9ce405591cad107bf3b10b502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9fe13d8172dedcc74c4407a4f2eec0834e9a0526a41e844755139f66b29f845 0.600000000000 1501567 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": 1033116, "vin": [ { "gen": { "height": 1033106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9fe13d8172dedcc74c4407a4f2eec0834e9a0526a41e844755139f66b29f845" } } ], "extra": [ 1, 116, 122, 238, 144, 238, 201, 133, 20, 162, 242, 244, 62, 51, 44, 45, 165, 34, 243, 4, 109, 249, 206, 64, 85, 145, 202, 209, 7, 191, 59, 16, 181, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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