Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 013ad413aa6d70612fdd735563b13dab93d1cdea8937a3a2cf9a85298240f6c8

Tx prefix hash: d0ca427d59fa1100f57ff134812a64667943780c207d69e87ddf359a5fb39562
Tx public key: 90f2909ed449c4d25fc7da840fdd7cbd7c2da8b6f543fffb463746fce613da62
Timestamp: 1724953882 Timestamp [UCT]: 2024-08-29 17:51:22 Age [y:d:h:m:s]: 00:231:04:10:04
Block: 1098617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165078 RingCT/type: yes/0
Extra: 0190f2909ed449c4d25fc7da840fdd7cbd7c2da8b6f543fffb463746fce613da62021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4279993d5c5f9009a8848c03c2073919b53c80c2f7b2dcdbcd5454c3af8b0f32 0.600000000000 1574394 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": 1098627, "vin": [ { "gen": { "height": 1098617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4279993d5c5f9009a8848c03c2073919b53c80c2f7b2dcdbcd5454c3af8b0f32" } } ], "extra": [ 1, 144, 242, 144, 158, 212, 73, 196, 210, 95, 199, 218, 132, 15, 221, 124, 189, 124, 45, 168, 182, 245, 67, 255, 251, 70, 55, 70, 252, 230, 19, 218, 98, 2, 17, 0, 0, 0, 2, 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