Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4255627e8fb25a3ca9c97d94faef3a8eea2a60f25c9168cbf37c66ee58ae5634

Tx prefix hash: e7986adb09c5399e14929f5761e07fc3de6044cdf86c582ec9278fe0a7d0b437
Tx public key: cd6554066b9afe594c2438d1cd9443e390b5bae681be69e0ae9e95275ffb8d5b
Timestamp: 1750308327 Timestamp [UCT]: 2025-06-19 04:45:27 Age [y:d:h:m:s]: 00:147:15:03:15
Block: 1308109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103329 RingCT/type: yes/0
Extra: 01cd6554066b9afe594c2438d1cd9443e390b5bae681be69e0ae9e95275ffb8d5b021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03057b7cf724ae9429cb2cfa387577f3451167edc2d155d7e1991e047250fd79 0.600000000000 1795722 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": 1308119, "vin": [ { "gen": { "height": 1308109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03057b7cf724ae9429cb2cfa387577f3451167edc2d155d7e1991e047250fd79" } } ], "extra": [ 1, 205, 101, 84, 6, 107, 154, 254, 89, 76, 36, 56, 209, 205, 148, 67, 227, 144, 181, 186, 230, 129, 190, 105, 224, 174, 158, 149, 39, 95, 251, 141, 91, 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