Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 243d710820dabc70c72643559036ba687dc5ff17fa6027ba4074ae1846324ce2

Tx prefix hash: 632e727bc747c6c763af23317f5c4ac2c6539dc67371c77c1913d6693590d6da
Tx public key: 181374448e1bd51b2e34a3e9d5283cb5d0ea117ab5f8d2107e4c0172a44d5f37
Timestamp: 1625396764 Timestamp [UCT]: 2021-07-04 11:06:04 Age [y:d:h:m:s]: 03:182:02:59:19
Block: 288105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899819 RingCT/type: yes/0
Extra: 01181374448e1bd51b2e34a3e9d5283cb5d0ea117ab5f8d2107e4c0172a44d5f3702110000000dd142c209000000000000000000

1 output(s) for total of 68.140627088000 dcy

stealth address amount amount idx
00: 0a45367740fff253201b0b8e43026f976101bb0d756728abae124fc227b384fa 68.140627088000 603601 of 0

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": 288115, "vin": [ { "gen": { "height": 288105 } } ], "vout": [ { "amount": 68140627088, "target": { "key": "0a45367740fff253201b0b8e43026f976101bb0d756728abae124fc227b384fa" } } ], "extra": [ 1, 24, 19, 116, 68, 142, 27, 213, 27, 46, 52, 163, 233, 213, 40, 60, 181, 208, 234, 17, 122, 181, 248, 210, 16, 126, 76, 1, 114, 164, 77, 95, 55, 2, 17, 0, 0, 0, 13, 209, 66, 194, 9, 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