Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b08b49d25e5fa4f212f15e7137f64beb7cad37d7974f8913e3a763d4dc061063

Tx prefix hash: f9bdbc71b6ef110580343d6c46430458776673a7663a5627200a0e9eddf37e3a
Tx public key: 243eb1c797e4fa90870a534e91acdddc4f1cc743b6434a912c99ec60009f73b9
Timestamp: 1707643744 Timestamp [UCT]: 2024-02-11 09:29:04 Age [y:d:h:m:s]: 00:315:21:16:07
Block: 955107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226190 RingCT/type: yes/0
Extra: 01243eb1c797e4fa90870a534e91acdddc4f1cc743b6434a912c99ec60009f73b902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600080000000 dcy

stealth address amount amount idx
00: 4c2a53e636171bcf383ea2d521d875e37d72785b1e0536d97a3cd151ad01c699 0.600080000000 1414391 of 0

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": 955117, "vin": [ { "gen": { "height": 955107 } } ], "vout": [ { "amount": 600080000, "target": { "key": "4c2a53e636171bcf383ea2d521d875e37d72785b1e0536d97a3cd151ad01c699" } } ], "extra": [ 1, 36, 62, 177, 199, 151, 228, 250, 144, 135, 10, 83, 78, 145, 172, 221, 220, 79, 28, 199, 67, 182, 67, 74, 145, 44, 153, 236, 96, 0, 159, 115, 185, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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