Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af7d4ea33af32610a0732b15ef706b46f59386dd9d7970ff88f0fac217542935

Tx prefix hash: 6d75d2d441ba2b40abcbbf3612b1857da9c42e1c005f26ed15c163c5d6bbe101
Tx public key: b8f3efb572c3b93bb6e6ebc0feaabc8213609bbcf759bd5c266fe8eff31aa8d5
Timestamp: 1755283010 Timestamp [UCT]: 2025-08-15 18:36:50 Age [y:d:h:m:s]: 00:005:23:56:31
Block: 1347376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4072 RingCT/type: yes/0
Extra: 01b8f3efb572c3b93bb6e6ebc0feaabc8213609bbcf759bd5c266fe8eff31aa8d502110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c968868a0edfcc41b7ab45a135f56fb2b0c969c6a45bfa42be7e1c42dacc3c9 0.600000000000 1835293 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": 1347386, "vin": [ { "gen": { "height": 1347376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c968868a0edfcc41b7ab45a135f56fb2b0c969c6a45bfa42be7e1c42dacc3c9" } } ], "extra": [ 1, 184, 243, 239, 181, 114, 195, 185, 59, 182, 230, 235, 192, 254, 170, 188, 130, 19, 96, 155, 188, 247, 89, 189, 92, 38, 111, 232, 239, 243, 26, 168, 213, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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