Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abf2b96668e25efd235f8659b67c3fb42330d5a5cdfd17a2076cc46414c86e4f

Tx prefix hash: ad0a918d09119720c335284516a22dbe276411768b7d757bdd07081ba550be23
Tx public key: be23e706410baeb2a1ef270d07086fd69c0f6b9585a80d1081a1e2a6cbc4f469
Timestamp: 1697704941 Timestamp [UCT]: 2023-10-19 08:42:21 Age [y:d:h:m:s]: 01:180:09:32:59
Block: 872919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389957 RingCT/type: yes/0
Extra: 01be23e706410baeb2a1ef270d07086fd69c0f6b9585a80d1081a1e2a6cbc4f46902110000000333af99f4000000000000000000

1 output(s) for total of 0.786424455000 dcy

stealth address amount amount idx
00: 357835e1afd33c97b8eeef918fab514f755d96c699cee8e61738a124a89a14f6 0.786424455000 1328029 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": 872929, "vin": [ { "gen": { "height": 872919 } } ], "vout": [ { "amount": 786424455, "target": { "key": "357835e1afd33c97b8eeef918fab514f755d96c699cee8e61738a124a89a14f6" } } ], "extra": [ 1, 190, 35, 231, 6, 65, 11, 174, 178, 161, 239, 39, 13, 7, 8, 111, 214, 156, 15, 107, 149, 133, 168, 13, 16, 129, 161, 226, 166, 203, 196, 244, 105, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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