Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4114fe42754534b08630a4c05678ad911d8f32d7dbf561f0a95ab510463de69a

Tx prefix hash: f46dd23143f27fb150c6bf1dcc7b9e96375c4c3d112e795af66737c7c16c2689
Tx public key: 87aa0cec0d4dc0f6c188ca12981c2ab371e8137334535213d7367801a5e5e968
Timestamp: 1607613206 Timestamp [UCT]: 2020-12-10 15:13:26 Age [y:d:h:m:s]: 03:355:03:25:36
Block: 159563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1004894 RingCT/type: yes/0
Extra: 0187aa0cec0d4dc0f6c188ca12981c2ab371e8137334535213d7367801a5e5e968021100000010aad74b3a000000000000000000

1 output(s) for total of 181.677951479000 dcy

stealth address amount amount idx
00: efdb77592d7666e34343817d7f091c1576873e280ad6c0d940d27dddcd7745b7 181.677951479000 279296 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": 159573, "vin": [ { "gen": { "height": 159563 } } ], "vout": [ { "amount": 181677951479, "target": { "key": "efdb77592d7666e34343817d7f091c1576873e280ad6c0d940d27dddcd7745b7" } } ], "extra": [ 1, 135, 170, 12, 236, 13, 77, 192, 246, 193, 136, 202, 18, 152, 28, 42, 179, 113, 232, 19, 115, 52, 83, 82, 19, 215, 54, 120, 1, 165, 229, 233, 104, 2, 17, 0, 0, 0, 16, 170, 215, 75, 58, 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