Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02b496a129f4715177f815826a1c2bc89833e114dab40f5c8525bef87387d5e7

Tx prefix hash: 53b79d573f6ebcb964d2c30bb8e46d13552c64dc89b704466ad095f7607928f0
Tx public key: 3df2ccf897d11f8ec248266b6319bd77643e3c4b2bcf64dac723fb327ca0b191
Timestamp: 1737397964 Timestamp [UCT]: 2025-01-20 18:32:44 Age [y:d:h:m:s]: 00:151:09:55:23
Block: 1201599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107913 RingCT/type: yes/0
Extra: 013df2ccf897d11f8ec248266b6319bd77643e3c4b2bcf64dac723fb327ca0b1910211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03924fa1dfdb50f648812691947f620fd059f58b18134c0890bb047294f3f364 0.600000000000 1688252 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": 1201609, "vin": [ { "gen": { "height": 1201599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03924fa1dfdb50f648812691947f620fd059f58b18134c0890bb047294f3f364" } } ], "extra": [ 1, 61, 242, 204, 248, 151, 209, 31, 142, 194, 72, 38, 107, 99, 25, 189, 119, 100, 62, 60, 75, 43, 207, 100, 218, 199, 35, 251, 50, 124, 160, 177, 145, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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