Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c1908b4f714a45595e2fc16b36293f2af2af3b4a8175389c3106f6cc3e16340

Tx prefix hash: 5f2b85f80e850ac6021286d9331aa14631abd03de3b4fd16452542a222ab166a
Tx public key: be4c471f203f70abbe37fc7704915e1824efb3a6d2dc08c01231752f794cc4f7
Timestamp: 1705267433 Timestamp [UCT]: 2024-01-14 21:23:53 Age [y:d:h:m:s]: 01:306:05:04:17
Block: 935396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477683 RingCT/type: yes/0
Extra: 01be4c471f203f70abbe37fc7704915e1824efb3a6d2dc08c01231752f794cc4f70211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f3d326c59df5f603b074a0133d1b4faaafdf352a6c29acfde30285890a753d2 0.600000000000 1393412 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": 935406, "vin": [ { "gen": { "height": 935396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f3d326c59df5f603b074a0133d1b4faaafdf352a6c29acfde30285890a753d2" } } ], "extra": [ 1, 190, 76, 71, 31, 32, 63, 112, 171, 190, 55, 252, 119, 4, 145, 94, 24, 36, 239, 179, 166, 210, 220, 8, 192, 18, 49, 117, 47, 121, 76, 196, 247, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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