Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fde2574798cbbb9f28da224a2f4a2d26a8de0c3e134f95963f23d2a3ea8943f

Tx prefix hash: a67132ca8107eac28e7724225ba01a2e59f6c7e9f69bc9fd55ca665f1864db65
Tx public key: f11e4345791d761cbff65482b5ccc36e59fc6a094cefd135d968baba54003726
Timestamp: 1711137203 Timestamp [UCT]: 2024-03-22 19:53:23 Age [y:d:h:m:s]: 00:362:07:21:18
Block: 984102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259037 RingCT/type: yes/0
Extra: 01f11e4345791d761cbff65482b5ccc36e59fc6a094cefd135d968baba540037260211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6095a041523751259f81700d84f22bdcaa2e4657416c34730e4cec80f2e47d1 0.600000000000 1444257 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": 984112, "vin": [ { "gen": { "height": 984102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6095a041523751259f81700d84f22bdcaa2e4657416c34730e4cec80f2e47d1" } } ], "extra": [ 1, 241, 30, 67, 69, 121, 29, 118, 28, 191, 246, 84, 130, 181, 204, 195, 110, 89, 252, 106, 9, 76, 239, 209, 53, 217, 104, 186, 186, 84, 0, 55, 38, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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