Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 548cb54fe2c74c4247c891d9acc33fdc99f82d37bceb365cbbaf6f1f162a663f

Tx prefix hash: 2a3b96a798898a874139ca4a49f3d1fed8b3fa0b02badcef04494633533ecc83
Tx public key: e634c18e824aace8ec86129a4a357ee144bf79a26fb34ec65107e3af52c3b7c7
Timestamp: 1697390652 Timestamp [UCT]: 2023-10-15 17:24:12 Age [y:d:h:m:s]: 01:100:21:05:45
Block: 870323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333303 RingCT/type: yes/0
Extra: 01e634c18e824aace8ec86129a4a357ee144bf79a26fb34ec65107e3af52c3b7c7021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.802155637000 dcy

stealth address amount amount idx
00: b9b9182fba8ece9238f79c88b63e362528c18210319ae87494a9ac1992b68e1f 0.802155637000 1325202 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": 870333, "vin": [ { "gen": { "height": 870323 } } ], "vout": [ { "amount": 802155637, "target": { "key": "b9b9182fba8ece9238f79c88b63e362528c18210319ae87494a9ac1992b68e1f" } } ], "extra": [ 1, 230, 52, 193, 142, 130, 74, 172, 232, 236, 134, 18, 154, 74, 53, 126, 225, 68, 191, 121, 162, 111, 179, 78, 198, 81, 7, 227, 175, 82, 195, 183, 199, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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