Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afac36635ee7b0f59a3d0bd4eabcd6924c7c1d719fd147593a0fba0ecee6ab50

Tx prefix hash: 3782450af2e9161b721a446c7a515f274c44cc01b37cd4367a5c02f48549f568
Tx public key: b540569c12c3aac7aa099a788e21f6740a1954bbd743a7dc2f28cd5e08090ec7
Timestamp: 1704721092 Timestamp [UCT]: 2024-01-08 13:38:12 Age [y:d:h:m:s]: 01:016:01:38:09
Block: 930880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272770 RingCT/type: yes/0
Extra: 01b540569c12c3aac7aa099a788e21f6740a1954bbd743a7dc2f28cd5e08090ec702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ee6583a7dce5619e0566d8bf67850ada0ea60a73f9bb408ef7af4826158f4c6 0.600000000000 1388770 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": 930890, "vin": [ { "gen": { "height": 930880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ee6583a7dce5619e0566d8bf67850ada0ea60a73f9bb408ef7af4826158f4c6" } } ], "extra": [ 1, 181, 64, 86, 156, 18, 195, 170, 199, 170, 9, 154, 120, 142, 33, 246, 116, 10, 25, 84, 187, 215, 67, 167, 220, 47, 40, 205, 94, 8, 9, 14, 199, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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