Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baa39410119db7aca7981e7f1f35bbdb93262e15ebd37afb5b4bc845076e3dc5

Tx prefix hash: f6cbc6366a8cf626063825d3271fbe0d0a527c582a5c4a25b145febeb801b7d9
Tx public key: ee19beff44369bb1f32f4b29b163957f0546bcdc85e85c4ec711b5fcecef259e
Timestamp: 1722796512 Timestamp [UCT]: 2024-08-04 18:35:12 Age [y:d:h:m:s]: 00:246:04:04:11
Block: 1080733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175826 RingCT/type: yes/0
Extra: 01ee19beff44369bb1f32f4b29b163957f0546bcdc85e85c4ec711b5fcecef259e02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4692e0470ec399ee5ff1c81a22465e20be95798267344a927bd3368d6a0c443 0.600000000000 1554206 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": 1080743, "vin": [ { "gen": { "height": 1080733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4692e0470ec399ee5ff1c81a22465e20be95798267344a927bd3368d6a0c443" } } ], "extra": [ 1, 238, 25, 190, 255, 68, 54, 155, 177, 243, 47, 75, 41, 177, 99, 149, 127, 5, 70, 188, 220, 133, 232, 92, 78, 199, 17, 181, 252, 236, 239, 37, 158, 2, 17, 0, 0, 0, 16, 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