Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5052eabef21c489aee78bc44ff8a28e02c6552bf89473a30289b2490df7c759

Tx prefix hash: bbbfd603ba9fe9fa7d2651c4ad340b81b52b348233cb4431d945c957dca2be02
Tx public key: ffdaa38a2a753691455aecf01f3ef7bad7bff8d956f1dcec30503188f18c4d17
Timestamp: 1761150432 Timestamp [UCT]: 2025-10-22 16:27:12 Age [y:d:h:m:s]: 00:022:12:18:46
Block: 1395601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16111 RingCT/type: yes/0
Extra: 01ffdaa38a2a753691455aecf01f3ef7bad7bff8d956f1dcec30503188f18c4d17021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d3d8e05b8d1f6ac2fbd8d838f6d2dee4ddba0cff67d93e213a4ebb61f690aab 0.600000000000 1883884 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": 1395611, "vin": [ { "gen": { "height": 1395601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d3d8e05b8d1f6ac2fbd8d838f6d2dee4ddba0cff67d93e213a4ebb61f690aab" } } ], "extra": [ 1, 255, 218, 163, 138, 42, 117, 54, 145, 69, 90, 236, 240, 31, 62, 247, 186, 215, 191, 248, 217, 86, 241, 220, 236, 48, 80, 49, 136, 241, 140, 77, 23, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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