Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01df7e5c32e12a57cfa1bec9deb31c5972953181321d5c5ac94a753fdb879666

Tx prefix hash: b41021415fc0a455bd2632b4f4a94b6561d4d127ea9c4f8e78f1c12c5dad81da
Tx public key: 621ea80fd083be82079e2fd4af5724216f5debf23e71cbd800d52b0a867b0ab5
Timestamp: 1766247380 Timestamp [UCT]: 2025-12-20 16:16:20 Age [y:d:h:m:s]: 00:001:11:48:32
Block: 1437835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1060 RingCT/type: yes/0
Extra: 01621ea80fd083be82079e2fd4af5724216f5debf23e71cbd800d52b0a867b0ab50211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5a4ba63feb987a3646ef931a45c35b8cf225a8aa586d743c79b59b51ed6687e 0.600000000000 1926646 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": 1437845, "vin": [ { "gen": { "height": 1437835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5a4ba63feb987a3646ef931a45c35b8cf225a8aa586d743c79b59b51ed6687e" } } ], "extra": [ 1, 98, 30, 168, 15, 208, 131, 190, 130, 7, 158, 47, 212, 175, 87, 36, 33, 111, 93, 235, 242, 62, 113, 203, 216, 0, 213, 43, 10, 134, 123, 10, 181, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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