Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e59472b75a133e6e7436c15f3fb9ba4f0302e4cb17cbe719faf210a17bd67c71

Tx prefix hash: b34decf86eb4fb0f2ffe738e33d6a9c16cdf57929480c13ebb4d0f599b7a1e79
Tx public key: 236c7e077476b12f0a681bf225b813b21c2e06c040a3e13b2f8b528cfeaa6f71
Timestamp: 1725525323 Timestamp [UCT]: 2024-09-05 08:35:23 Age [y:d:h:m:s]: 00:258:21:10:56
Block: 1103365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184904 RingCT/type: yes/0
Extra: 01236c7e077476b12f0a681bf225b813b21c2e06c040a3e13b2f8b528cfeaa6f71021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e715dbe392e4a98db58923faf1fca8436503373fc4dab1f9796bf1636112980 0.600000000000 1580164 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": 1103375, "vin": [ { "gen": { "height": 1103365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e715dbe392e4a98db58923faf1fca8436503373fc4dab1f9796bf1636112980" } } ], "extra": [ 1, 35, 108, 126, 7, 116, 118, 177, 47, 10, 104, 27, 242, 37, 184, 19, 178, 28, 46, 6, 192, 64, 163, 225, 59, 47, 139, 82, 140, 254, 170, 111, 113, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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