Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a2ecdc752577aac898ce278a0ab0fdef507ec92a178920b5478bf373fb61970

Tx prefix hash: fcfdd2204c0e8621eb23aea98cd253fd5b505a5572d4c2cdb2cf2cb3e3102f6a
Tx public key: 0dad57c71d2a23fd7b60c07a2011407588fe750798424eb502cf63fae304871f
Timestamp: 1699379870 Timestamp [UCT]: 2023-11-07 17:57:50 Age [y:d:h:m:s]: 01:143:02:04:19
Block: 886610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363452 RingCT/type: yes/0
Extra: 010dad57c71d2a23fd7b60c07a2011407588fe750798424eb502cf63fae304871f02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.708423605000 dcy

stealth address amount amount idx
00: 35e45db490d9aea18231747def297ca8d0348c7271d58cffcc57aa1c2d3340d5 0.708423605000 1342439 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": 886620, "vin": [ { "gen": { "height": 886610 } } ], "vout": [ { "amount": 708423605, "target": { "key": "35e45db490d9aea18231747def297ca8d0348c7271d58cffcc57aa1c2d3340d5" } } ], "extra": [ 1, 13, 173, 87, 199, 29, 42, 35, 253, 123, 96, 192, 122, 32, 17, 64, 117, 136, 254, 117, 7, 152, 66, 78, 181, 2, 207, 99, 250, 227, 4, 135, 31, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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