Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32da2612ba4ffaa12c5c14dab45b3318cc554b6fe52d20f858c93b2fac58e848

Tx prefix hash: 4f59cb88b6fffb5026c92e378ddc099b9f1a1080ceff08072f3f402e3ad4961a
Tx public key: b0a8ae2de229558e1550bcd0a391a7d9367d76aaea8267c745f1371b61877448
Timestamp: 1745771281 Timestamp [UCT]: 2025-04-27 16:28:01 Age [y:d:h:m:s]: 00:206:14:18:16
Block: 1270700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145365 RingCT/type: yes/0
Extra: 01b0a8ae2de229558e1550bcd0a391a7d9367d76aaea8267c745f1371b618774480211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a9f0b73208f5682c322308e3991d1ccd55da507b3eadd4a7192e1a4d4ab1df2 0.600000000000 1757945 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": 1270710, "vin": [ { "gen": { "height": 1270700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a9f0b73208f5682c322308e3991d1ccd55da507b3eadd4a7192e1a4d4ab1df2" } } ], "extra": [ 1, 176, 168, 174, 45, 226, 41, 85, 142, 21, 80, 188, 208, 163, 145, 167, 217, 54, 125, 118, 170, 234, 130, 103, 199, 69, 241, 55, 27, 97, 135, 116, 72, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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