Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832f6868e62fbfc1a528e53a149ebd64c50477d818df63e6ba95d6bfcb539f92

Tx prefix hash: 053511ad90fd1a17129c8450bd4fc4fd3bc401f2f4056584193a1e8b89c7eceb
Tx public key: a4d72f8334660341a63cbe71821defc957bdcfeec9f7289c312b7c9266732e6a
Timestamp: 1745609269 Timestamp [UCT]: 2025-04-25 19:27:49 Age [y:d:h:m:s]: 00:011:22:05:11
Block: 1269361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8512 RingCT/type: yes/0
Extra: 01a4d72f8334660341a63cbe71821defc957bdcfeec9f7289c312b7c9266732e6a0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df633934de650636860c306492b25d85cfc0f08a3000c4de0f263bae62b06d14 0.600000000000 1756596 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": 1269371, "vin": [ { "gen": { "height": 1269361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df633934de650636860c306492b25d85cfc0f08a3000c4de0f263bae62b06d14" } } ], "extra": [ 1, 164, 215, 47, 131, 52, 102, 3, 65, 166, 60, 190, 113, 130, 29, 239, 201, 87, 189, 207, 238, 201, 247, 40, 156, 49, 43, 124, 146, 102, 115, 46, 106, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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