Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94bc5c307397dc203729364b915f7ce01f04a7fc49eea700a54b08fc491a77b3

Tx prefix hash: f9310ef8482630b99b70bf7c9d672f66add225ac3010204c1182e58a10d1a5ea
Tx public key: 5ec68b89cf46baed9ac7bdd7e98cff3212a89b1866baaa72936f5b52ff238b5b
Timestamp: 1726711992 Timestamp [UCT]: 2024-09-19 02:13:12 Age [y:d:h:m:s]: 00:066:16:20:54
Block: 1113200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47666 RingCT/type: yes/0
Extra: 015ec68b89cf46baed9ac7bdd7e98cff3212a89b1866baaa72936f5b52ff238b5b021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a9a816eee9f405239575bcd191ccb8c135ad2d9273afb0a52d76cdd4e095f71 0.600000000000 1592789 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": 1113210, "vin": [ { "gen": { "height": 1113200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a9a816eee9f405239575bcd191ccb8c135ad2d9273afb0a52d76cdd4e095f71" } } ], "extra": [ 1, 94, 198, 139, 137, 207, 70, 186, 237, 154, 199, 189, 215, 233, 140, 255, 50, 18, 168, 155, 24, 102, 186, 170, 114, 147, 111, 91, 82, 255, 35, 139, 91, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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