Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5719aef1ba1361a04c839d79bab583d0c2554408ecf63498e52a31ae8e74d16e

Tx prefix hash: 9c39f0a682ab2f9f02c3c7ecc1e5efa23a4930186348e9de8f512873aa9027e3
Tx public key: 1a52eb9925658382a85fc0fc4aa420fd5d91f09103a2df648d0c2a666cd44390
Timestamp: 1708095178 Timestamp [UCT]: 2024-02-16 14:52:58 Age [y:d:h:m:s]: 01:044:10:05:17
Block: 958854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292777 RingCT/type: yes/0
Extra: 011a52eb9925658382a85fc0fc4aa420fd5d91f09103a2df648d0c2a666cd4439002110000000252d47e94000000000000000000

1 output(s) for total of 0.600710000000 dcy

stealth address amount amount idx
00: 8c51e1555f6b49d4af16989bca13273e164c5715626312f85faa5aa9a668b189 0.600710000000 1418263 of 0

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": 958864, "vin": [ { "gen": { "height": 958854 } } ], "vout": [ { "amount": 600710000, "target": { "key": "8c51e1555f6b49d4af16989bca13273e164c5715626312f85faa5aa9a668b189" } } ], "extra": [ 1, 26, 82, 235, 153, 37, 101, 131, 130, 168, 95, 192, 252, 74, 164, 32, 253, 93, 145, 240, 145, 3, 162, 223, 100, 141, 12, 42, 102, 108, 212, 67, 144, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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