Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a226eccd2c619917fb9b1d57db9117ef80ab2ac90b2b5ab80c222600eec446bc

Tx prefix hash: 01c762f75a630d800feecac7647758bd86c753a0e92a72f6cee8fbf0d9530c4c
Tx public key: e576c1f70d88ad89b2a2e7e5c99d4a8af59addf3c9a50dbf5464d34c12e69df6
Timestamp: 1724504723 Timestamp [UCT]: 2024-08-24 13:05:23 Age [y:d:h:m:s]: 00:224:13:50:03
Block: 1094911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160352 RingCT/type: yes/0
Extra: 01e576c1f70d88ad89b2a2e7e5c99d4a8af59addf3c9a50dbf5464d34c12e69df6021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cd37d0f79292e9adb36b9c7da5732baf94f3bb586260cf87c0aa1740d02f01a 0.600000000000 1570032 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": 1094921, "vin": [ { "gen": { "height": 1094911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cd37d0f79292e9adb36b9c7da5732baf94f3bb586260cf87c0aa1740d02f01a" } } ], "extra": [ 1, 229, 118, 193, 247, 13, 136, 173, 137, 178, 162, 231, 229, 201, 157, 74, 138, 245, 154, 221, 243, 201, 165, 13, 191, 84, 100, 211, 76, 18, 230, 157, 246, 2, 17, 0, 0, 0, 4, 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