Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a662f0665bc9bd4cd0a15d021a959b8fa8a44912755462667f9d274e4bd8e45e

Tx prefix hash: b30ed503271d496fbb5f9fa477f9600fd7eabbea0f7b85a464984db44bb7a440
Tx public key: 53a2d09fa254d9805ff55039ba3a2b3b05fc63e472091c529e3dda566b47f641
Timestamp: 1708949793 Timestamp [UCT]: 2024-02-26 12:16:33 Age [y:d:h:m:s]: 01:043:18:30:36
Block: 965949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292300 RingCT/type: yes/0
Extra: 0153a2d09fa254d9805ff55039ba3a2b3b05fc63e472091c529e3dda566b47f64102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62f025e8837b96708eeb15f1fdc7fb8aea7c803b923566bd75083120d3ea86fc 0.600000000000 1425704 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": 965959, "vin": [ { "gen": { "height": 965949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62f025e8837b96708eeb15f1fdc7fb8aea7c803b923566bd75083120d3ea86fc" } } ], "extra": [ 1, 83, 162, 208, 159, 162, 84, 217, 128, 95, 245, 80, 57, 186, 58, 43, 59, 5, 252, 99, 228, 114, 9, 28, 82, 158, 61, 218, 86, 107, 71, 246, 65, 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