Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb786e66249f57b377eba92a6213e92de4c2c2a99d6210069345a9e035690aa6

Tx prefix hash: 089cab641c243d7aee7adcf9632fd1e81ff1c15134d30727d0f139e0b624df78
Tx public key: ea71b69862321d10adb05eafde42dc278a9c1431e2c1ac1f1192f8e9ae4f5566
Timestamp: 1711753033 Timestamp [UCT]: 2024-03-29 22:57:13 Age [y:d:h:m:s]: 01:248:06:20:46
Block: 989203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436127 RingCT/type: yes/0
Extra: 01ea71b69862321d10adb05eafde42dc278a9c1431e2c1ac1f1192f8e9ae4f55660211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36741c5a1b14f76b392a568de911ef62f61e17ad43cbdf36c22801755c16c767 0.600000000000 1449498 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": 989213, "vin": [ { "gen": { "height": 989203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36741c5a1b14f76b392a568de911ef62f61e17ad43cbdf36c22801755c16c767" } } ], "extra": [ 1, 234, 113, 182, 152, 98, 50, 29, 16, 173, 176, 94, 175, 222, 66, 220, 39, 138, 156, 20, 49, 226, 193, 172, 31, 17, 146, 248, 233, 174, 79, 85, 102, 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