Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649ddd0a5cb20e03f861d6e8e30471c03bb8e6010fc184edf9ff1c8f4b2fe571

Tx prefix hash: 774a70c1bbdecb1a699281e5edb1c81583cf1996d884fb68b91318839c6c4d90
Tx public key: 11ea7aedcda48b3c9861da18b9ca96a860138607798ad115c46c2aa16d7c24ae
Timestamp: 1762962880 Timestamp [UCT]: 2025-11-12 15:54:40 Age [y:d:h:m:s]: 00:040:15:03:36
Block: 1410615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29080 RingCT/type: yes/0
Extra: 0111ea7aedcda48b3c9861da18b9ca96a860138607798ad115c46c2aa16d7c24ae021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49168a5397b9897a4edc55530bd33afb8034ad3cebde70cc0e28faf97379be6e 0.600000000000 1899068 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": 1410625, "vin": [ { "gen": { "height": 1410615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49168a5397b9897a4edc55530bd33afb8034ad3cebde70cc0e28faf97379be6e" } } ], "extra": [ 1, 17, 234, 122, 237, 205, 164, 139, 60, 152, 97, 218, 24, 185, 202, 150, 168, 96, 19, 134, 7, 121, 138, 209, 21, 196, 108, 42, 161, 109, 124, 36, 174, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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