Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a916c3d91faf250a4c676e493e4d9c4693fd39d427c3ee09f41c523aff76f3

Tx prefix hash: b12e59d4cf12ca144a66b2ba334ee8dd1595228ce9210eb9d50a24695627d058
Tx public key: a3ecfb67bb8a60cae551b48c63fa93de6e1002ef7b04aeab26b0ebabd3e3b111
Timestamp: 1766620199 Timestamp [UCT]: 2025-12-24 23:49:59 Age [y:d:h:m:s]: 00:011:14:16:17
Block: 1440917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8310 RingCT/type: yes/0
Extra: 01a3ecfb67bb8a60cae551b48c63fa93de6e1002ef7b04aeab26b0ebabd3e3b1110211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad5ab1953a12da335f73193b5c7b7d4822f01849d70fe77cd369e644509f6af7 0.600000000000 1929808 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": 1440927, "vin": [ { "gen": { "height": 1440917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad5ab1953a12da335f73193b5c7b7d4822f01849d70fe77cd369e644509f6af7" } } ], "extra": [ 1, 163, 236, 251, 103, 187, 138, 96, 202, 229, 81, 180, 140, 99, 250, 147, 222, 110, 16, 2, 239, 123, 4, 174, 171, 38, 176, 235, 171, 211, 227, 177, 17, 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