Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2854be926600866f7872f86061fb71aedb458489bd360043b9a5c54164058ee

Tx prefix hash: 3dda0eb8950b64cc811bd08b7cfa943a204a1d8a7deff446c47919f80591c6cf
Tx public key: a2d12073f4a324e2ebfca766a9bae7a08a077c65f41030a552e9bcb0f7fe1b54
Timestamp: 1707063740 Timestamp [UCT]: 2024-02-04 16:22:20 Age [y:d:h:m:s]: 01:073:22:24:35
Block: 950295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313917 RingCT/type: yes/0
Extra: 01a2d12073f4a324e2ebfca766a9bae7a08a077c65f41030a552e9bcb0f7fe1b5402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f892af80abff6aeb8b51fb285f67a18c190b8642cb735404cb54377b0940769 0.600000000000 1408891 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": 950305, "vin": [ { "gen": { "height": 950295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f892af80abff6aeb8b51fb285f67a18c190b8642cb735404cb54377b0940769" } } ], "extra": [ 1, 162, 209, 32, 115, 244, 163, 36, 226, 235, 252, 167, 102, 169, 186, 231, 160, 138, 7, 124, 101, 244, 16, 48, 165, 82, 233, 188, 176, 247, 254, 27, 84, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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