Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a11137c6774cd562eae32c27de305221dd6d4f105cd8361e18ffcaef24bc462

Tx prefix hash: 4bb5eb4dac24f3dbfc2dc0cfc915ae988e0245939087c85b7147b41889300972
Tx public key: 41425f7b80624220e70d0fba47a7e03e23d6ad2483b47a5de65a8dadb72f8efe
Timestamp: 1757944716 Timestamp [UCT]: 2025-09-15 13:58:36 Age [y:d:h:m:s]: 00:108:22:40:18
Block: 1369030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78012 RingCT/type: yes/0
Extra: 0141425f7b80624220e70d0fba47a7e03e23d6ad2483b47a5de65a8dadb72f8efe021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 117e081c74837c4eb82f61b2715f0be76e4fd642fa2437a0a239dbf86a5a63d6 0.600000000000 1857099 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": 1369040, "vin": [ { "gen": { "height": 1369030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "117e081c74837c4eb82f61b2715f0be76e4fd642fa2437a0a239dbf86a5a63d6" } } ], "extra": [ 1, 65, 66, 95, 123, 128, 98, 66, 32, 231, 13, 15, 186, 71, 167, 224, 62, 35, 214, 173, 36, 131, 180, 122, 93, 230, 90, 141, 173, 183, 47, 142, 254, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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