Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b476031c310896ce495c963769e35f99c0b662d3d7fbadd08a62230c2bca34

Tx prefix hash: 207e7ce96fc51edc5854e232d4c124706f3705d215eb2c0da30e92cc5db2df13
Tx public key: 58a5ca8cdd0748ce4bd690e871dc2c9ab3020da8a17777d29c7f24f6455e8402
Timestamp: 1723082996 Timestamp [UCT]: 2024-08-08 02:09:56 Age [y:d:h:m:s]: 00:076:13:19:45
Block: 1083112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54810 RingCT/type: yes/0
Extra: 0158a5ca8cdd0748ce4bd690e871dc2c9ab3020da8a17777d29c7f24f6455e840202110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b0faab7c32076b2a95c1b8896eb673db14995c74aad912d5a51704983f037c 0.600000000000 1556947 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": 1083122, "vin": [ { "gen": { "height": 1083112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b0faab7c32076b2a95c1b8896eb673db14995c74aad912d5a51704983f037c" } } ], "extra": [ 1, 88, 165, 202, 140, 221, 7, 72, 206, 75, 214, 144, 232, 113, 220, 44, 154, 179, 2, 13, 168, 161, 119, 119, 210, 156, 127, 36, 246, 69, 94, 132, 2, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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