Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db892d1540da163d7224fadfed82f1e601782c0a3ed3532926509ee27273e862

Tx prefix hash: d30b76ca16ba7ba23e11548a2a319aa6dc926df458170aaf5505bffe95387922
Tx public key: fe9aa697ccc285c15b0021588f7e67f7ad5353f96439869fb13e9dc5c5ef5e9a
Timestamp: 1713848591 Timestamp [UCT]: 2024-04-23 05:03:11 Age [y:d:h:m:s]: 00:253:07:07:30
Block: 1006561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181299 RingCT/type: yes/0
Extra: 01fe9aa697ccc285c15b0021588f7e67f7ad5353f96439869fb13e9dc5c5ef5e9a0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3685c3117a1b300aea5ff5bb1a1fc408389bba20df18ba9fe0f964f2e7a9d86 0.600000000000 1467627 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": 1006571, "vin": [ { "gen": { "height": 1006561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3685c3117a1b300aea5ff5bb1a1fc408389bba20df18ba9fe0f964f2e7a9d86" } } ], "extra": [ 1, 254, 154, 166, 151, 204, 194, 133, 193, 91, 0, 33, 88, 143, 126, 103, 247, 173, 83, 83, 249, 100, 57, 134, 159, 177, 62, 157, 197, 197, 239, 94, 154, 2, 17, 0, 0, 0, 6, 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