Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0a1e7a4c6098c994d5e83846449762d794cf5313a3f74dff68af077a19f177

Tx prefix hash: 8050c3216cb3df09a0e5a2f99238a66dc8780b723cb713915a2838a26729255d
Tx public key: 3a3fd3e5342135fa88a42c619fbc415eb85afe6fd815e58911ce74f2780885f2
Timestamp: 1713175437 Timestamp [UCT]: 2024-04-15 10:03:57 Age [y:d:h:m:s]: 01:198:18:32:34
Block: 1000967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400734 RingCT/type: yes/0
Extra: 013a3fd3e5342135fa88a42c619fbc415eb85afe6fd815e58911ce74f2780885f20211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31bc8f3e576ac7afa4508f7ce0a7850ff625b4d7bfbf09e6cd48407913a800db 0.600000000000 1461467 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": 1000977, "vin": [ { "gen": { "height": 1000967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31bc8f3e576ac7afa4508f7ce0a7850ff625b4d7bfbf09e6cd48407913a800db" } } ], "extra": [ 1, 58, 63, 211, 229, 52, 33, 53, 250, 136, 164, 44, 97, 159, 188, 65, 94, 184, 90, 254, 111, 216, 21, 229, 137, 17, 206, 116, 242, 120, 8, 133, 242, 2, 17, 0, 0, 0, 9, 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