Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6644c8625e2fb319910eb7526a7ccb7194e0116c8ba785937cf18ffcbcbdb283

Tx prefix hash: c7d5f8b59925b273b383e72d36ccea22c363d20fe2f2d9b54418dfb26420e11c
Tx public key: 6ab1253dd07041dd38ce9e2819ed95a561d2eb1b86f210c7dddaa2aea059d9b9
Timestamp: 1707705415 Timestamp [UCT]: 2024-02-12 02:36:55 Age [y:d:h:m:s]: 00:315:03:20:24
Block: 955616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225654 RingCT/type: yes/0
Extra: 016ab1253dd07041dd38ce9e2819ed95a561d2eb1b86f210c7dddaa2aea059d9b90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63562d47415a16c6704fadad2e35e149e3d72f54622fe24a801da2d7f8e6cac3 0.600000000000 1414914 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": 955626, "vin": [ { "gen": { "height": 955616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63562d47415a16c6704fadad2e35e149e3d72f54622fe24a801da2d7f8e6cac3" } } ], "extra": [ 1, 106, 177, 37, 61, 208, 112, 65, 221, 56, 206, 158, 40, 25, 237, 149, 165, 97, 210, 235, 27, 134, 242, 16, 199, 221, 218, 162, 174, 160, 89, 217, 185, 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