Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc5441322171db1d1b614c8693778a56014c4d0bfdc037c6ce71f12b5c16e14b

Tx prefix hash: 52180a015183d3bc20cd3875f7590af5f5a85a5a4276a024c4aa00e89160649b
Tx public key: 1f5bd9486cd7d066cae265161ea385d2d7dd7b2eb3bfeaff369bad9314e531e4
Timestamp: 1725585225 Timestamp [UCT]: 2024-09-06 01:13:45 Age [y:d:h:m:s]: 00:079:06:50:28
Block: 1103863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56692 RingCT/type: yes/0
Extra: 011f5bd9486cd7d066cae265161ea385d2d7dd7b2eb3bfeaff369bad9314e531e4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c5a546063c318e802bea5c3154aefcb692314ede16b2408d804855e5f7d774d 0.600000000000 1580856 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": 1103873, "vin": [ { "gen": { "height": 1103863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c5a546063c318e802bea5c3154aefcb692314ede16b2408d804855e5f7d774d" } } ], "extra": [ 1, 31, 91, 217, 72, 108, 215, 208, 102, 202, 226, 101, 22, 30, 163, 133, 210, 215, 221, 123, 46, 179, 191, 234, 255, 54, 155, 173, 147, 20, 229, 49, 228, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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