Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3142e775795418b94b0a2aa2a97a62fbb469f86197bc0c864271a80f61e5878c

Tx prefix hash: 704f4fae3fde63f3ab53be74b4aa5802c330987f53810f540277be1f6ea79319
Tx public key: fb2322eaa3fa58591f40908039f9f322ffc86d8ca4d752ed671953ceabf172b8
Timestamp: 1699512102 Timestamp [UCT]: 2023-11-09 06:41:42 Age [y:d:h:m:s]: 01:187:01:11:08
Block: 887707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394899 RingCT/type: yes/0
Extra: 01fb2322eaa3fa58591f40908039f9f322ffc86d8ca4d752ed671953ceabf172b802110000000633af99f4000000000000000000

1 output(s) for total of 0.702519212000 dcy

stealth address amount amount idx
00: 534d384bec553fd061f2fd3287b8d7408deb6ea982374878d4dec8887b9033fa 0.702519212000 1343602 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": 887717, "vin": [ { "gen": { "height": 887707 } } ], "vout": [ { "amount": 702519212, "target": { "key": "534d384bec553fd061f2fd3287b8d7408deb6ea982374878d4dec8887b9033fa" } } ], "extra": [ 1, 251, 35, 34, 234, 163, 250, 88, 89, 31, 64, 144, 128, 57, 249, 243, 34, 255, 200, 109, 140, 164, 215, 82, 237, 103, 25, 83, 206, 171, 241, 114, 184, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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