Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4990f6945d64cf58260f259a2b0ecf4f74e17009bf37c405b71d68b21e7e157

Tx prefix hash: 551d251a1d25048209785e59ec0b45ad9611c463dc71d23fa5b85553ebfd38b1
Tx public key: b0a62f2cb8ac4c3d634d50059a3b25ad5c28303ae0a1a08e7e2f60b41beee8bc
Timestamp: 1745138215 Timestamp [UCT]: 2025-04-20 08:36:55 Age [y:d:h:m:s]: 00:166:10:19:35
Block: 1265448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116611 RingCT/type: yes/0
Extra: 01b0a62f2cb8ac4c3d634d50059a3b25ad5c28303ae0a1a08e7e2f60b41beee8bc021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f655c054d81b5a454480e257481946e1ebabb1518ab96e1aef2a9c5baa5cf56d 0.600000000000 1752657 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": 1265458, "vin": [ { "gen": { "height": 1265448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f655c054d81b5a454480e257481946e1ebabb1518ab96e1aef2a9c5baa5cf56d" } } ], "extra": [ 1, 176, 166, 47, 44, 184, 172, 76, 61, 99, 77, 80, 5, 154, 59, 37, 173, 92, 40, 48, 58, 224, 161, 160, 142, 126, 47, 96, 180, 27, 238, 232, 188, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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