Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be416625c8ef24e6746f5722e4feba4e83eff6850fce16e851e2b52c7b92368c

Tx prefix hash: 123f89fab736cf44cb42d48cd7916e84cf69788d46a79462a8b43e18a362f87e
Tx public key: 51f09ec01f5f7edf8438f9d06852c34bf315ec5420c35a0e141178cfd6f080b9
Timestamp: 1742080990 Timestamp [UCT]: 2025-03-15 23:23:10 Age [y:d:h:m:s]: 00:316:05:24:05
Block: 1240174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223626 RingCT/type: yes/0
Extra: 0151f09ec01f5f7edf8438f9d06852c34bf315ec5420c35a0e141178cfd6f080b90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1d7330ac032e11a3210c8b0fa1140bcdc6e35483c74802509be9ecd0bd6d61c 0.600000000000 1727139 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": 1240184, "vin": [ { "gen": { "height": 1240174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1d7330ac032e11a3210c8b0fa1140bcdc6e35483c74802509be9ecd0bd6d61c" } } ], "extra": [ 1, 81, 240, 158, 192, 31, 95, 126, 223, 132, 56, 249, 208, 104, 82, 195, 75, 243, 21, 236, 84, 32, 195, 90, 14, 20, 17, 120, 207, 214, 240, 128, 185, 2, 17, 0, 0, 0, 2, 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