Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d76a9669ad3af41f71efd72688f637e4c089f934b619906343817b4a6a6bdb7c

Tx prefix hash: d6dfa315041875d9a6751b0f4d718e9aff73b9dd64000bdf969f05e671a49dd9
Tx public key: 3c3f90b5480e23ed7215eb7404c3c2aa12dc8f410c0c34a259bdd51016c22eee
Timestamp: 1676177667 Timestamp [UCT]: 2023-02-12 04:54:27 Age [y:d:h:m:s]: 02:056:00:50:28
Block: 695133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561633 RingCT/type: yes/0
Extra: 013c3f90b5480e23ed7215eb7404c3c2aa12dc8f410c0c34a259bdd51016c22eee0211000000015029cbac000000000000000000

1 output(s) for total of 3.053062732000 dcy

stealth address amount amount idx
00: a1c68bfa84255afc51dbd00cb5dd38f4e33ec87f41436b4f3d317170c29e6191 3.053062732000 1138076 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": 695143, "vin": [ { "gen": { "height": 695133 } } ], "vout": [ { "amount": 3053062732, "target": { "key": "a1c68bfa84255afc51dbd00cb5dd38f4e33ec87f41436b4f3d317170c29e6191" } } ], "extra": [ 1, 60, 63, 144, 181, 72, 14, 35, 237, 114, 21, 235, 116, 4, 195, 194, 170, 18, 220, 143, 65, 12, 12, 52, 162, 89, 189, 213, 16, 22, 194, 46, 238, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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