Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a0c852c3315a4265addb79d0ea5c59199caafa9df596900180edbdd9cb4023

Tx prefix hash: 209ddcec9971eeaae2e34526826224076c4db00e108c1125ec9d03d83e165fe8
Tx public key: 8dfd0b6bb833109f709dfad72012c6735ae57e61de0f18f586b2f773bd5aae00
Timestamp: 1713790863 Timestamp [UCT]: 2024-04-22 13:01:03 Age [y:d:h:m:s]: 01:054:19:26:37
Block: 1006076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300036 RingCT/type: yes/0
Extra: 018dfd0b6bb833109f709dfad72012c6735ae57e61de0f18f586b2f773bd5aae0002110000001159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ef6aabc9229bf907f4dd345b84b289486488a3aae738c81dffb883b9c941614 0.600000000000 1466986 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": 1006086, "vin": [ { "gen": { "height": 1006076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ef6aabc9229bf907f4dd345b84b289486488a3aae738c81dffb883b9c941614" } } ], "extra": [ 1, 141, 253, 11, 107, 184, 51, 16, 159, 112, 157, 250, 215, 32, 18, 198, 115, 90, 229, 126, 97, 222, 15, 24, 245, 134, 178, 247, 115, 189, 90, 174, 0, 2, 17, 0, 0, 0, 17, 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