Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6403c1d680100291390765a88ac2c2bf4d90f949fe1e0517f52dc5326dbf1567

Tx prefix hash: ddfc20d3b1b8a84e232d93a22d3d71911a57d8afedeba32277615f40290c96c1
Tx public key: 637f0d0cdcb06acb3dafed17ff76d0091b38a7343085717d8e16f6e93ad5e28a
Timestamp: 1701608014 Timestamp [UCT]: 2023-12-03 12:53:34 Age [y:d:h:m:s]: 01:199:18:56:48
Block: 905077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403831 RingCT/type: yes/0
Extra: 01637f0d0cdcb06acb3dafed17ff76d0091b38a7343085717d8e16f6e93ad5e28a02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.615324432000 dcy

stealth address amount amount idx
00: 531e3e44c8a03da239e3e350d19f61769bcb5b8843a8dc2f31404b1d178df4a7 0.615324432000 1361942 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": 905087, "vin": [ { "gen": { "height": 905077 } } ], "vout": [ { "amount": 615324432, "target": { "key": "531e3e44c8a03da239e3e350d19f61769bcb5b8843a8dc2f31404b1d178df4a7" } } ], "extra": [ 1, 99, 127, 13, 12, 220, 176, 106, 203, 61, 175, 237, 23, 255, 118, 208, 9, 27, 56, 167, 52, 48, 133, 113, 125, 142, 22, 246, 233, 58, 213, 226, 138, 2, 17, 0, 0, 0, 13, 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