Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18bc945c2473f1d676e15a2b1a29eb21b1b86b470bf3424dc43cf499146c3d3a

Tx prefix hash: 4bc308e2eea6d1e228ed01576a53b5e477cadab70060e13c1ddd4aa3aecadfa3
Tx public key: 3a3fced1dfeb70dd0966da426dcc9702cae85206fdced141360119fa8f4355a0
Timestamp: 1683225316 Timestamp [UCT]: 2023-05-04 18:35:16 Age [y:d:h:m:s]: 01:357:16:32:34
Block: 752933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516891 RingCT/type: yes/0
Extra: 013a3fced1dfeb70dd0966da426dcc9702cae85206fdced141360119fa8f4355a0021100000003b3164c24000000000000000000

1 output(s) for total of 1.964357876000 dcy

stealth address amount amount idx
00: 208d1e46f4c3eaed51d726e1bcdc9c1c488a7045dcede8bc5ee1d464e5b477dc 1.964357876000 1201134 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": 752943, "vin": [ { "gen": { "height": 752933 } } ], "vout": [ { "amount": 1964357876, "target": { "key": "208d1e46f4c3eaed51d726e1bcdc9c1c488a7045dcede8bc5ee1d464e5b477dc" } } ], "extra": [ 1, 58, 63, 206, 209, 223, 235, 112, 221, 9, 102, 218, 66, 109, 204, 151, 2, 202, 232, 82, 6, 253, 206, 209, 65, 54, 1, 25, 250, 143, 67, 85, 160, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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