Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c066be9ce06f84e4ecc47a5747c41c8e08c6207d4be3b77af1593d14565e057

Tx prefix hash: 580c1947dd319ac654999d103ac69cc6df49354c8dbe91bfbb6aa7924f2dcbfd
Tx public key: fae96034703862f4ddef1aa30f896bf2aa0f12c56754265a0a915fd40540b443
Timestamp: 1723512936 Timestamp [UCT]: 2024-08-13 01:35:36 Age [y:d:h:m:s]: 00:239:03:49:37
Block: 1086680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170802 RingCT/type: yes/0
Extra: 01fae96034703862f4ddef1aa30f896bf2aa0f12c56754265a0a915fd40540b44302110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee5747b1732bff5922181b7e1f0135001511fb1c34bd5942051f8464f245e4ce 0.600000000000 1561279 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": 1086690, "vin": [ { "gen": { "height": 1086680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee5747b1732bff5922181b7e1f0135001511fb1c34bd5942051f8464f245e4ce" } } ], "extra": [ 1, 250, 233, 96, 52, 112, 56, 98, 244, 221, 239, 26, 163, 15, 137, 107, 242, 170, 15, 18, 197, 103, 84, 38, 90, 10, 145, 95, 212, 5, 64, 180, 67, 2, 17, 0, 0, 0, 9, 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