Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f3c2db3725306181a507d0148017f4fbd36b9f7d7d514c3ddc9089856ca37fe

Tx prefix hash: d99f6cb6642c062dec958485b839b6f261b1fbf904f2ad34142547fd1af664a2
Tx public key: de68e0b4c74fffaa492d4338e2ba2e87cdc410a82fdbd76db8bc3301abfee9d8
Timestamp: 1722939437 Timestamp [UCT]: 2024-08-06 10:17:17 Age [y:d:h:m:s]: 00:200:10:23:48
Block: 1081921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143100 RingCT/type: yes/0
Extra: 01de68e0b4c74fffaa492d4338e2ba2e87cdc410a82fdbd76db8bc3301abfee9d802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d16cd3dbcdd62a072c501d9ebfd3d882fbbe86aac05155d491f09cfd85e2cf88 0.600000000000 1555744 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": 1081931, "vin": [ { "gen": { "height": 1081921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d16cd3dbcdd62a072c501d9ebfd3d882fbbe86aac05155d491f09cfd85e2cf88" } } ], "extra": [ 1, 222, 104, 224, 180, 199, 79, 255, 170, 73, 45, 67, 56, 226, 186, 46, 135, 205, 196, 16, 168, 47, 219, 215, 109, 184, 188, 51, 1, 171, 254, 233, 216, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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