Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5168c5ebc9ba76033601587f98ae7198bea5303f512dc7891a92d1d6b55d784

Tx prefix hash: bca7b6a401b4dec6f55adf133e5b5390c6192b808a943b15d939664a956ce4b0
Tx public key: 154c87e62458e234a24cd3d4a5f80e858495af21e89464a41025901f9e705313
Timestamp: 1714053616 Timestamp [UCT]: 2024-04-25 14:00:16 Age [y:d:h:m:s]: 00:350:18:44:39
Block: 1008253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250771 RingCT/type: yes/0
Extra: 01154c87e62458e234a24cd3d4a5f80e858495af21e89464a41025901f9e7053130211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9d9a668c10f0700399f2d87cbf6e6e15402af4ac4e2bbae7df1b8a794e734ff 0.600000000000 1469721 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": 1008263, "vin": [ { "gen": { "height": 1008253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9d9a668c10f0700399f2d87cbf6e6e15402af4ac4e2bbae7df1b8a794e734ff" } } ], "extra": [ 1, 21, 76, 135, 230, 36, 88, 226, 52, 162, 76, 211, 212, 165, 248, 14, 133, 132, 149, 175, 33, 232, 148, 100, 164, 16, 37, 144, 31, 158, 112, 83, 19, 2, 17, 0, 0, 0, 9, 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