Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adaf8a3ecaceeea616ab44c50dbc3adc671d6130e05cc4d5a76f524922706bb7

Tx prefix hash: 9b50f25060ab013f405dbb34e10713177641cb06ced020be1ffdaf3afe3c9507
Tx public key: adf2234dd1f8b8e6f0b99ec51961d8c6672c9ecaf9d9a1537219a7afa1dd000d
Timestamp: 1706534080 Timestamp [UCT]: 2024-01-29 13:14:40 Age [y:d:h:m:s]: 01:055:01:15:55
Block: 945893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300424 RingCT/type: yes/0
Extra: 01adf2234dd1f8b8e6f0b99ec51961d8c6672c9ecaf9d9a1537219a7afa1dd000d02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0310b70a9a07781b3c4a17726b1d8150c524f32f42dbfb3f4823732a6314c91b 0.600000000000 1404217 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": 945903, "vin": [ { "gen": { "height": 945893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0310b70a9a07781b3c4a17726b1d8150c524f32f42dbfb3f4823732a6314c91b" } } ], "extra": [ 1, 173, 242, 35, 77, 209, 248, 184, 230, 240, 185, 158, 197, 25, 97, 216, 198, 103, 44, 158, 202, 249, 217, 161, 83, 114, 25, 167, 175, 161, 221, 0, 13, 2, 17, 0, 0, 0, 8, 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