Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d9d4d367ce419f3c96aa890c96f37a0d14e55430feaeed282e1dcadced5861

Tx prefix hash: bd65f748aa16d2e7359176759726bf54cd766c224d636ad529510717c470011f
Tx public key: 7708cbb567d18b313bb0bbae7fb7de7a88cbb0c109a94ccdd584e11673bdae7d
Timestamp: 1649279146 Timestamp [UCT]: 2022-04-06 21:05:46 Age [y:d:h:m:s]: 02:342:22:06:15
Block: 474673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 764651 RingCT/type: yes/0
Extra: 017708cbb567d18b313bb0bbae7fb7de7a88cbb0c109a94ccdd584e11673bdae7d021100000001c9067537000000000000000000

1 output(s) for total of 16.413891091000 dcy

stealth address amount amount idx
00: 47f35580b1f293d1f9e1abc250f4e978bcd0a1f378b1b731470424045c7943f1 16.413891091000 894754 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": 474683, "vin": [ { "gen": { "height": 474673 } } ], "vout": [ { "amount": 16413891091, "target": { "key": "47f35580b1f293d1f9e1abc250f4e978bcd0a1f378b1b731470424045c7943f1" } } ], "extra": [ 1, 119, 8, 203, 181, 103, 209, 139, 49, 59, 176, 187, 174, 127, 183, 222, 122, 136, 203, 176, 193, 9, 169, 76, 205, 213, 132, 225, 22, 115, 189, 174, 125, 2, 17, 0, 0, 0, 1, 201, 6, 117, 55, 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