Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 315c6e8b7aa23b3e46f41ca6c2145d8a357200cfcbbae77bfbde3a64ec8ef516

Tx prefix hash: ab6a4ce14b686738091421445c9a64f2fc25cb654d6b66b993859248ac6ee50b
Tx public key: ebc2b56f0dd3756afd9b7ef35080a045336e9dec6c5499b2baabef73ae6e0b9c
Timestamp: 1765975881 Timestamp [UCT]: 2025-12-17 12:51:21 Age [y:d:h:m:s]: 00:012:14:52:50
Block: 1435578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9037 RingCT/type: yes/0
Extra: 01ebc2b56f0dd3756afd9b7ef35080a045336e9dec6c5499b2baabef73ae6e0b9c0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 200afab670cb43809c2adcf7aaed0967cd9cac7412e291542ac8e2eaca8d743e 0.600000000000 1924375 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": 1435588, "vin": [ { "gen": { "height": 1435578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "200afab670cb43809c2adcf7aaed0967cd9cac7412e291542ac8e2eaca8d743e" } } ], "extra": [ 1, 235, 194, 181, 111, 13, 211, 117, 106, 253, 155, 126, 243, 80, 128, 160, 69, 51, 110, 157, 236, 108, 84, 153, 178, 186, 171, 239, 115, 174, 110, 11, 156, 2, 17, 0, 0, 0, 2, 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