Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78f834afb6c96b7f586b79fcf6028ecc0c15534609daaf6545c366baaac057bd

Tx prefix hash: 5a2a641d06b63e9ec22793989dcb914a9d9004775a6d68062b5c285bc0555958
Tx public key: a07790d184a8414de921ba2bcb7d907dcb5c894cb5157160dc5139947fb44a6a
Timestamp: 1759218471 Timestamp [UCT]: 2025-09-30 07:47:51 Age [y:d:h:m:s]: 00:007:21:33:29
Block: 1379571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5649 RingCT/type: yes/0
Extra: 01a07790d184a8414de921ba2bcb7d907dcb5c894cb5157160dc5139947fb44a6a02110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61dea0ff4675677f75d9bf144f09e5de340410d5afe0a1a5a2ad130f647ce9fd 0.600000000000 1867670 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": 1379581, "vin": [ { "gen": { "height": 1379571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61dea0ff4675677f75d9bf144f09e5de340410d5afe0a1a5a2ad130f647ce9fd" } } ], "extra": [ 1, 160, 119, 144, 209, 132, 168, 65, 77, 233, 33, 186, 43, 203, 125, 144, 125, 203, 92, 137, 76, 181, 21, 113, 96, 220, 81, 57, 148, 127, 180, 74, 106, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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