Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f48f984dca47d2d01f1d9dd7d298dc3bd330f081f1fc656ad8d9cc25b565420d

Tx prefix hash: a8b9f22402baf2ea0d3b5f00cc6db1cfe28d17067b26bdcf12566e2b49a53ffb
Tx public key: 0ac8cdc3a0bb3964b5300b9050cade58afd24a0e77fc40fc823037928da4e89a
Timestamp: 1754388505 Timestamp [UCT]: 2025-08-05 10:08:25 Age [y:d:h:m:s]: 00:097:15:05:02
Block: 1340719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68734 RingCT/type: yes/0
Extra: 010ac8cdc3a0bb3964b5300b9050cade58afd24a0e77fc40fc823037928da4e89a0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f1cab618d77e7b2d94a8fb836ba920c3058a1e5198082b1d324ecaabcfd9b80 0.600000000000 1828538 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": 1340729, "vin": [ { "gen": { "height": 1340719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f1cab618d77e7b2d94a8fb836ba920c3058a1e5198082b1d324ecaabcfd9b80" } } ], "extra": [ 1, 10, 200, 205, 195, 160, 187, 57, 100, 181, 48, 11, 144, 80, 202, 222, 88, 175, 210, 74, 14, 119, 252, 64, 252, 130, 48, 55, 146, 141, 164, 232, 154, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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