Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8be6298efe0993feef50e98d2eebc110902680769b9c7849eed81304f76cfbd1

Tx prefix hash: 10a1ce765eff7f98415090b452d937cb7505de9d2e47e8aa52cb4c0e3dd7f3c5
Tx public key: 613fb06bafb9a21351b6991fb447464bdaab65c6565f1ad876166140de61360c
Timestamp: 1682528711 Timestamp [UCT]: 2023-04-26 17:05:11 Age [y:d:h:m:s]: 02:202:18:47:14
Block: 747155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 664770 RingCT/type: yes/0
Extra: 01613fb06bafb9a21351b6991fb447464bdaab65c6565f1ad876166140de61360c0211000000017e406890000000000000000000

1 output(s) for total of 2.052889311000 dcy

stealth address amount amount idx
00: 8f0fb58107d094f4e8b8eba7d6eee3e8b2bb96429aedf2b7017a5a211aa16f92 2.052889311000 1194798 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": 747165, "vin": [ { "gen": { "height": 747155 } } ], "vout": [ { "amount": 2052889311, "target": { "key": "8f0fb58107d094f4e8b8eba7d6eee3e8b2bb96429aedf2b7017a5a211aa16f92" } } ], "extra": [ 1, 97, 63, 176, 107, 175, 185, 162, 19, 81, 182, 153, 31, 180, 71, 70, 75, 218, 171, 101, 198, 86, 95, 26, 216, 118, 22, 97, 64, 222, 97, 54, 12, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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