Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2a791a1a9f040aa3514bd451d4acbbc87899d07fc80c8361c2bca001c117fa

Tx prefix hash: 88966b7fbfff2bf41867094b0e3012a09cbb14e9ff383121998c656d58e78740
Tx public key: 5b1d90a05d3e5471853bb1e7f506279d35602fffee6504f014cf70ebc5f3a6b2
Timestamp: 1764737732 Timestamp [UCT]: 2025-12-03 04:55:32 Age [y:d:h:m:s]: 00:001:08:39:07
Block: 1425319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 996 RingCT/type: yes/0
Extra: 015b1d90a05d3e5471853bb1e7f506279d35602fffee6504f014cf70ebc5f3a6b2021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ff89a9deccf9149e7d923dc1309dca73478eea0f5854d9c93f331c942589f79 0.600000000000 1913952 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": 1425329, "vin": [ { "gen": { "height": 1425319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ff89a9deccf9149e7d923dc1309dca73478eea0f5854d9c93f331c942589f79" } } ], "extra": [ 1, 91, 29, 144, 160, 93, 62, 84, 113, 133, 59, 177, 231, 245, 6, 39, 157, 53, 96, 47, 255, 238, 101, 4, 240, 20, 207, 112, 235, 197, 243, 166, 178, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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