Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c20c5f6898cb319c41ac6b9c936423a36654a83ae5a6719e888dd5ba47a4b7f

Tx prefix hash: 0c70c6547cd25c02ce36cf48adc8ea5e81c178008e83f1aa79c85f274287758b
Tx public key: 5fadd64122d116ecc7b5ca62b8ea075d94c9b8c455f651dd8912759f6e4a21bd
Timestamp: 1706327916 Timestamp [UCT]: 2024-01-27 03:58:36 Age [y:d:h:m:s]: 01:284:02:48:41
Block: 944181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461849 RingCT/type: yes/0
Extra: 015fadd64122d116ecc7b5ca62b8ea075d94c9b8c455f651dd8912759f6e4a21bd0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5861c960b7e50b4eb91d9606da8934eda7670e821514d1ce891637f6804fbdb2 0.600000000000 1402415 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": 944191, "vin": [ { "gen": { "height": 944181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5861c960b7e50b4eb91d9606da8934eda7670e821514d1ce891637f6804fbdb2" } } ], "extra": [ 1, 95, 173, 214, 65, 34, 209, 22, 236, 199, 181, 202, 98, 184, 234, 7, 93, 148, 201, 184, 196, 85, 246, 81, 221, 137, 18, 117, 159, 110, 74, 33, 189, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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