Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1051ac977dd335d068279e19966d83c542413ed49c0f605d6248d35af35f257

Tx prefix hash: 62f489133e013f95092930af91eaac35bba65d91eb99e6a53b843961c411f02e
Tx public key: b9c21c3158031ed41b1147f0cab2c351fd871aaee2d9dfef4878f6f839298489
Timestamp: 1718702189 Timestamp [UCT]: 2024-06-18 09:16:29 Age [y:d:h:m:s]: 00:296:18:32:23
Block: 1046802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212072 RingCT/type: yes/0
Extra: 01b9c21c3158031ed41b1147f0cab2c351fd871aaee2d9dfef4878f6f8392984890211000000050bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb7d3a339231da8e876d69ae59dd2d95d9694d078325a99ce516d6c73085ba10 0.600000000000 1516621 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": 1046812, "vin": [ { "gen": { "height": 1046802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb7d3a339231da8e876d69ae59dd2d95d9694d078325a99ce516d6c73085ba10" } } ], "extra": [ 1, 185, 194, 28, 49, 88, 3, 30, 212, 27, 17, 71, 240, 202, 178, 195, 81, 253, 135, 26, 174, 226, 217, 223, 239, 72, 120, 246, 248, 57, 41, 132, 137, 2, 17, 0, 0, 0, 5, 11, 186, 22, 215, 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