Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a2a3c3b59190b19bef18c8135283ce981203b9e54c6284778aa77191164e00a

Tx prefix hash: f9c97676834d36af72f469788fb64cd52895f722a2a6fc19a6dd32792236d72e
Tx public key: 7e52adec3f69905aa5f75775a45b80cc99d5b202cfc470529d9fc8e6f78b48e8
Timestamp: 1726231079 Timestamp [UCT]: 2024-09-13 12:37:59 Age [y:d:h:m:s]: 00:072:10:06:16
Block: 1109212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51784 RingCT/type: yes/0
Extra: 017e52adec3f69905aa5f75775a45b80cc99d5b202cfc470529d9fc8e6f78b48e802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4a39573871f53dd19137365f0fb6915a9d5f2f9a2e141eebdb70c2a924b63c0 0.600000000000 1587381 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": 1109222, "vin": [ { "gen": { "height": 1109212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4a39573871f53dd19137365f0fb6915a9d5f2f9a2e141eebdb70c2a924b63c0" } } ], "extra": [ 1, 126, 82, 173, 236, 63, 105, 144, 90, 165, 247, 87, 117, 164, 91, 128, 204, 153, 213, 178, 2, 207, 196, 112, 82, 157, 159, 200, 230, 247, 139, 72, 232, 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