Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 169f02d89c5e78bb821117090099f2c5f17d37effac1d8a0a94d352637bc09b9

Tx prefix hash: 92af2e1743c3d663e3f8912d279af0191c921ffe80effa6d87fb6be266417aa4
Tx public key: ac0fd6731553231e0f63e4d5b0243b5c2a8323b291a203249933e46da15125cb
Timestamp: 1703620893 Timestamp [UCT]: 2023-12-26 20:01:33 Age [y:d:h:m:s]: 01:101:03:34:57
Block: 921765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333402 RingCT/type: yes/0
Extra: 01ac0fd6731553231e0f63e4d5b0243b5c2a8323b291a203249933e46da15125cb02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c928f61a2a19796f05c830514183023df9e4bb53229ef0fcc30286c8e835aec7 0.600000000000 1379459 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": 921775, "vin": [ { "gen": { "height": 921765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c928f61a2a19796f05c830514183023df9e4bb53229ef0fcc30286c8e835aec7" } } ], "extra": [ 1, 172, 15, 214, 115, 21, 83, 35, 30, 15, 99, 228, 213, 176, 36, 59, 92, 42, 131, 35, 178, 145, 162, 3, 36, 153, 51, 228, 109, 161, 81, 37, 203, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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