Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e69a93a58ae87e9c0c1dbe88973523e4975b013b11920eed6771c4cc133d2b86

Tx prefix hash: 92e5873a0122a9d9d28fc19380053d8c9e3b0b999169b000e8f2f0f3aee0a83a
Tx public key: 22dabfd5864053840f83c7a59f67f4afce99fb12f6cf1a663a4514fbd754af78
Timestamp: 1724854944 Timestamp [UCT]: 2024-08-28 14:22:24 Age [y:d:h:m:s]: 00:222:17:20:14
Block: 1097801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159032 RingCT/type: yes/0
Extra: 0122dabfd5864053840f83c7a59f67f4afce99fb12f6cf1a663a4514fbd754af78021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49160a3d7866544d05d87ca85eff5edba6aa5ee4be691e56899dc0d370244df9 0.600000000000 1573296 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": 1097811, "vin": [ { "gen": { "height": 1097801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49160a3d7866544d05d87ca85eff5edba6aa5ee4be691e56899dc0d370244df9" } } ], "extra": [ 1, 34, 218, 191, 213, 134, 64, 83, 132, 15, 131, 199, 165, 159, 103, 244, 175, 206, 153, 251, 18, 246, 207, 26, 102, 58, 69, 20, 251, 215, 84, 175, 120, 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